home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
InfoMagic Standards 1994 January
/
InfoMagic Standards - January 1994.iso
/
ccitt
/
1988
/
troff
/
3_7_09.tro
< prev
next >
Wrap
Text File
|
1991-12-12
|
93KB
|
3,574 lines
.rs
.\" Troff code generated by TPS Convert from ITU Original Files
.\" Not Copyright ( c) 1991
.\"
.\" Assumes tbl, eqn, MS macros, and lots of luck.
.TA 1c 2c 3c 4c 5c 6c 7c 8c
.ds CH
.ds CF
.EQ
delim @@
.EN
.nr LL 40.5P
.nr ll 40.5P
.nr HM 3P
.nr FM 6P
.nr PO 4P
.nr PD 9p
.po 4P
.rs
\v | 5i'
.sp 2P
.LP
\fBRecommendation\ I.253\fR
.RT
.sp 2P
.sp 1P
.ce 1000
\fBCALL\ COMPLETION\ SUPPLEMENTARY\ SERVICES\fR
.EF '% Fascicle\ III.7\ \(em\ Rec.\ I.253''
.OF '''Fascicle\ III.7\ \(em\ Rec.\ I.253 %'
.ce 0
.sp 1P
.ce 1000
\fI(Melbourne, 1988)\fR
.sp 9p
.RT
.ce 0
.sp 1P
.PP
The purpose of this Recommendation is to provide the stage 1
description of the method defined in Recommendation\ I.130 using the means
given in Recommendation\ I.210.
.sp 1P
.RT
.PP
Supplementary services are described by a prose definition and
description (step\ 1.1) and by a dynamic description (step\ 1.3). The application
of the attribute technique, as defined in Recommendation\ I.140, for
supplementary services is for futher study.
.PP
This Recommendation describes the following Call Completion
supplementary services:
.RT
.LP
I.253.1
Call Waiting (CW)
.LP
I.253.2
Call Hold (HOLD)
.LP
I.253.3
Completion of calls to busy subscribers (CCBS)
(Note)
.PP
\fINote\fR \ \(em\ This service already identified needs to be further
studied; its description is not yet included.
.sp 2P
.LP
\fB1\fR I.253.1\ \(em
\fBCall Waiting\fR
.sp 1P
.RT
.sp 1P
.LP
1.1
\fIDefinition\fR
.sp 9p
.RT
.PP
The Call Waiting service permits a subscriber to be notified of an incoming
call (as per basic call procedures) with an indication that no
interface information channel is available. The user then has the choice of
accepting, rejecting or ignoring the waiting call (as per basic call
procedures).
.RT
.sp 2P
.LP
1.2
\fIDescription\fR
.sp 1P
.RT
.sp 1P
.LP
1.2.1
\fIGeneral description\fR
.sp 9p
.RT
.PP
The ISDN Call Waiting service allows an out\(hyof\(hyband notification
to subscriber\ B of the incoming call; this is the assumed case for this
definition. In addition, as a service provider option, audible in\(hyband
indications may be provided to the channels occupied with the speech bearer
service and the Telephony teleservice. Where applied, tones should be in
accordance with Recommendation\ E.180.
.PP
The maximum number of calls that can be handled (e.g.\ active,
held, alerting, waiting) for each ISDN number on a given interface is specified
at subscription time.
.RT
.sp 1P
.LP
1.2.2
\fISpecific terminology\fR
.sp 9p
.RT
.PP
Throughout this definition the following terminology will be
used:
.PP
Subscriber\ B:\ the subscriber who is provided by the network with the
Call Waiting service\fR on a particular interface.
.PP
User\ B:\ the user who reacts to the call\fR waiting at B.
.PP
User\ C:\ the user who has originated a call to B which causes
the Call Waiting service\fR to be invoked.
.PP
User\ A:\ represents a user who is engaged in a call with user B
(this call can be in any\fR state).
.PP
User Response timer T1:\ this timer specifies the period the network
will wait for a positive response, from a terminal at B, to the offered
call. It is part of the basic call and has a value of a few seconds.
.PP
No Answer timer T2:\ this optional timer specifies the period the
network will wait for a response (answer), from user B, to the offered call
from user\ C. The value of this timer is between 0.5 and 2\ minutes.
.RT
.sp 1P
.LP
1.2.3
\fIQualifications on the applicability to telecommunication\fR
\fIservices\fR
.sp 9p
.RT
.PP
This supplementary service is considered meaningful when
applied to the Telephony teleservice and the speech and 3.1 kHz audio
bearer services. Furthermore, it may also be meaningful when applied to
other services.
.bp
.RT
.sp 2P
.LP
1.3
\fIProcedures\fR
.sp 1P
.RT
.sp 1P
.LP
1.3.1
\fIProvisionB/Fwithdrawal\fR
.sp 9p
.RT
.PP
Call Waiting can be provided on a subscription basis or, as a
network provider option, can be generally available to all users without
subscription. Call Waiting can be withdrawn for administrative
reasons.
.PP
As part of each applicable bearer service or teleservice, there is
an option specifying the maximum number of information channels which can be
used (occupied) on the interface for each ISDN number, all ISDN numbers or
subsets of ISDN numbers. Call Waiting for bearer services or teleservices
occurs only when an attempt is made to exceed these limits.
.PP
As a network provider option, Call Waiting can be offered with
several subscription options. The options apply separately to each ISDN
number and service combination. For each subscription option, only one
value can be
selected. Subscription options are summarized below:
.RT
.LP
.sp 1
\fISubscription options\fR \fIValue\fR Calls that can wait
\(em
All
\(em
Others are for further study
Calling user receives notification call is waiting
\(em
No
\(em
Yes
.PP
In addition, the following subscription options can be specified for each
ISDN number, all ISDN numbers, or subsets of ISDN numbers on each
interface.
.LP
.sp 1
\fISubscription options\fR \fIValue\fR Maximum number of calls which can
be waiting
\(em
One
\(em
\fIl\fR , where 1 \(= \fIl\fR \(= \fIn\fR \(em \fIm\fR
.PP
\fINote\fR \ \(em\ The parameters \fIm\fR | (maximum number of information
channels) and \fIn\fR | (maximum number of total calls present) are defined
in the relevant basic service description (refer to Recommendations\ I.231
and\ I.241).
.sp 2P
.LP
\fR 1.3.2
\fINormal procedures\fR
.sp 1P
.RT
.sp 1P
.LP
1.3.2.1
\fIActivationB/Fdeactivation\fR
.sp 9p
.RT
.PP
Subscriber B may activate and deactivate Call Waiting with an
appropriate request. Whether, and if so, to what degree,
activationB/Fdeactivation is supported by the network may be network dependent.
If supported, then the network shall inform subscriber\ B (all terminals
on the access) of the success, or other outcome, of this action.
.RT
.sp 1P
.LP
1.3.2.2
\fIInvocation\fR \v'2p'
.sp 9p
.RT
.LP
1.3.2.2.1\ \ When an incoming call from user C arrives at the access
of subscriber\ B and encounters the channels busy condition, and a network
determined user busy (NDUB) condition does not result, then the Call Waiting
service will be invoked and the call shall be offered to subscriber\ B
with an indication that the channels busy condition exists.
.bp
.sp 1P
.LP
1.3.2.3
\fIOperation\fR \v'2p'
.sp 9p
.RT
.LP
1.3.2.3.1\ \ If a response is received from a terminal at the B access,
within the normal basic call period, that the user(s) is (are) being informed
about the incoming call, then user C will be given an indication that the
called user(s) is (are) being informed of the incoming call. In some networks
this indication may also indicate that call waiting is in operation.
.LP
1.3.2.3.2\ \ If user B requests connection to the waiting call and placement
of the specified active call with user A into a held state, before the
expiry of the optional No Answer timer T2, then the call between user\
C and user\ B is completed in the normal manner with any indications to
user\ C being removed.
The previously active call between user\ A and user\ B is put into the held
state. User\ A may be given an indication that his call has been put into the
held state.
.PP
\fINote\fR \ \(em\ From this state other supplementary services, for example
the Three Party Service, may be used.
.LP
1.3.2.3.3\ \ If user B requests connection to the waiting call and
termination of the specified active call with user\ A before the expiry
of the optional No Answer timer T2, then the call between user\ C and user\
B is
completed in the normal manner with any indications to user\ C being removed.
The previously active call between user\ A and user\ B is terminated in the
normal manner.
.LP
1.3.2.3.4\ \ If user B terminates the active call with user A before the
expiry of the optional No Answer timer T2, then this call shall be released
in the normal manner. User\ B is then able to accept the waiting call from
user\ C using normal information channel selection procedures.
.LP
1.3.2.3.5\ \ If user B holds the active call with user A before the
expiry of the optional No Answer timer T2, then this call shall be held
in the normal manner. User\ B is then able to accept the waiting call from
user\ C
using normal information channel selection procedures.
.LP
1.3.2.3.6\ \ If user A requests termination of the active call with user\ B
before the expiry of the optional No Answer timer T2, then the conditions
of \fR \(sc\ 1.3.2.3.4 apply.
.sp 2P
.LP
1.3.3
\fIExceptional procedures\fR
.sp 1P
.RT
.sp 1P
.LP
1.3.3.1
\fIActivationB/FdeactivationB/Fregistration\fR
.sp 9p
.RT
.PP
None identified.
.RT
.sp 1P
.LP
1.3.3.2
\fIInvocation\fR
.sp 9p
.RT
.PP
None identified.
.RT
.sp 2P
.LP
1.3.3.3
\fIOperation\fR
.sp 1P
.RT
.sp 1P
.LP
1.3.3.3.1
\fIIncoming call from user C ignored by subscriber B\fR
.sp 9p
.RT
.PP
If the optional No Answer timer T2 expires without any acceptance from
subscriber\ B of the incoming call, then the network shall inform
subscriber\ B that the call is no longer waiting and also inform user\
C that his call cannot be connected. Normal release applies to the call
attempt from
user\ C (the call is cleared indicating no response) with an appropriate
indication given to user\ C.
.RT
.sp 1P
.LP
1.3.3.3.2
\fIIncoming call from user C rejected by user B\fR
.sp 9p
.RT
.PP
A rejection of the waiting call by one of the terminals on the
interface of subscriber\ B will not stop the optional No Answer timer T2 as
another terminal may subsequently accept the waiting call within the remainder
of the specified period. Such a rejection may, however, cancel any indication
provided to that terminal. Where rejections of a waiting call have been
received from all those terminals that responded with an alerting indication
before the expiry of the optional No Answer timer T2, then the network shall
inform user\ C that his call cannot be connected. Normal release applies
to the call attempt from user\ C with the call being cleared indicating
user rejection. Subscriber\ B is notified that the call is no longer waiting.
.RT
.sp 1P
.LP
1.3.3.3.3
\fIRelease by user C within the specified period\fR
.sp 9p
.RT
.PP
If calling user C informs the network, before the expiry of the
optional No Answer timer T2, that he wishes to release his call attempt to
subscriber\ B, then the network shall inform subscriber\ B of this situation
and initiate release of the call attempt from user\ C.
.bp
.RT
.sp 1P
.LP
1.3.3.3.4
\fINo positive response from terminals at subscriber B's\fR
\fIinterface\fR
.sp 9p
.RT
.PP
If no positive response that user(s) are being informed of the
waiting call is received from a terminal at subscriber\ B's interface during
the normal call period (User Response timer T1), then the call attempt from
user\ C shall be released by the network with user\ C being given the reason
for the release.
.RT
.sp 1P
.LP
1.3.3.3.5
\fINo resources available\fR
.sp 9p
.RT
.PP
If user B accepts a call and network resources do not exist to
complete the call (i.e.\ no information channels are available), the network
will indicate an error to user\ B with cause \*Qno B\(hychannels available\*U.
The
network will not clear the call but will wait for another user\ B indication
for acceptance, until user C clears the call or the optional No Answer
timer T2
expires.
.RT
.sp 2P
.LP
1.3.4
\fIAlternative procedures\fR
.sp 1P
.RT
.sp 1P
.LP
1.3.4.1
\fIActivationB/FdeactivationB/Fregistration\fR
.sp 9p
.RT
.PP
None identified.
.RT
.sp 1P
.LP
1.3.4.2
\fIInvocation and operation\fR
.sp 9p
.RT
.PP
None identified.
.RT
.sp 2P
.LP
1.4
\fINetwork capabilities for charging\fR
.sp 1P
.RT
.PP
This Recommendation does not cover charging principles. Future
Recommendations in the D\(hySeries are expected to contain that information.
.PP
It shall be possible to charge the subscriber accurately for the
service.
.RT
.sp 2P
.LP
1.5
\fIInterworking requirements\fR
.sp 1P
.RT
.sp 1P
.LP
1.5.1
\fIISDN served user: non\(hyISDN calling user\fR
.sp 9p
.RT
.PP
If an ISDN subscriber B receives a call from a non\(hyISDN calling
user, the network will send the Call Waiting indication to subscriber\
B in the normal way.
.PP
An inband indication will be applied to channels occupied with the
3.1\ kHz audio bearer service (where the call originated from the PSTN as
identified by a progress indicator), only if it is destined to a number
designated for inband notification by the call waiting subscriber.
.RT
.sp 1P
.LP
1.5.2
\fINon\(hyISDN served user: ISDN calling user\fR
.sp 9p
.RT
.PP
Not applicable since a non\(hyISDN served user will not be able to
subscribe to ISDN Call Waiting.
.RT
.sp 2P
.LP
1.6
\fIInteraction with other supplementary services\fR
.sp 1P
.RT
.sp 1P
.LP
1.6.1
\fICall Waiting\fR
.sp 9p
.RT
.PP
Not relevant.
.RT
.sp 1P
.LP
1.6.2
\fICall Transfer\fR
.sp 9p
.RT
.PP
User B, who has subscribed to both Call Waiting and Call Transfer services,
cannot transfer a waiting call from user\ C until he first establishes
a connection to user\ C.
.PP
Assume that user\ B is on an active call with user\ A and has
received an indication of a waiting call from user\ C. Users\ A and\ B
have Call Waiting subscribed for their accesses and user\ B has subscribed
to the Call
Transfer service. User\ B intends to transfer user\ A to user\ D.
.bp
.RT
.LP
\(em
User B may receive an indication of a waiting call from
user\ C either before or during the transfer of user\ A to another
party. The call waiting indication may be presented regardless of the
type of transfer invoked by user B (i.e.\ for Normal, Single Step, or
Explicit transfers). When user\ A has been transferred, a B\(hychannel
would normally become idle, enabling the waiting call to be answered
by user\ B.
.LP
\fR \(em
If user A has a call waiting indication before or during
the transfer process, then upon successful completion of the transfer of
user\ A to user\ D, user\ A shall retain the waiting call indication.
User A could use normal call waiting procedures (if desired) to accept
the waiting call.
.LP
\(em
If user D receives a call waiting indication during the
transfer process, e.g.\ while being in a call with user B, then
upon successful completion of the transfer of user A to user D,
user D shall retain the waiting call indication. User D could use normal
call waiting procedures (if desired) to accept the waiting
call.
.PP
In general, a call waiting indication may be delivered to users\ A or\
B (and to user\ D during the transfer process) when the called user has
subscribed to the Call Waiting service.
.sp 1P
.LP
1.6.3
\fIConnected Line Identification Presentation\fR
.sp 9p
.RT
.PP
No impact, i.e. neither supplementary service affects the
operation of the other supplementary service.
.PP
When user B uses one of the call waiting procedures to accept a
waiting call (within any time limits established by the service provider),
user\ C will be informed of the connection. The confirmation that a connection
has been established may provide the connected user\ B's number.
.RT
.sp 1P
.LP
1.6.4
\fIConnected Line Identification Restriction\fR
.sp 9p
.RT
.PP
No impact, i.e. neither supplementary service affects the
operation of the other supplementary service.
.RT
.sp 1P
.LP
1.6.5
\fICalling Line Identification Presentation\fR
.sp 9p
.RT
.PP
No impact, i.e. neither supplementary service affects the
operation of the other supplementary service.
.PP
If the user(s) at B is(are) given a call waiting indication, and
has(have) subscribed to the CLIP service, then the calling user number shall
be presented to the users at B at the time the call waiting indication is
given.
.RT
.sp 1P
.LP
1.6.6
\fICalling Line Identification Restriction\fR
.sp 9p
.RT
.PP
No impact, i.e. neither supplementary service affects the
operation of the other supplementary service.
.PP
Assume a user at C, who has subscribed to the CLIR service, reaches a user(s)
at\ B, who has subscribed to the Call Waiting service. On invocation,
the user at\ B would receive a call waiting indication but would not receive
user\ C's number when the call waiting indication is given.
.RT
.sp 1P
.LP
1.6.7
\fIClosed User Group\fR
.sp 9p
.RT
.PP
No impact, i.e. neither supplementary service affects the
operation of the other supplementary service.
.RT
.sp 1P
.LP
1.6.8
\fIConference Calling\fR
.sp 9p
.RT
.PP
A user at B who is active on any type of conference call may
receive an indication of a waiting call.
.PP
Once a conference has been established:
.RT
.LP
i)
Any party that has activated Call Waiting will be able to
receive an indication of an incoming call, and could place his connection to
the conference on hold to accept the waiting call.
.LP
ii)
The Conference Controller could, if desired, add the party from the waiting
call, by answering the waiting call and using the \*Qadd party from existing
call\*U procedures.
.bp
.sp 1P
.LP
1.6.9
\fIDirect\(hyDialling\(hyIn\fR
.sp 9p
.RT
.PP
No impact, i.e. neither supplementary service affects the
operation of the other supplementary service.
.RT
.sp 2P
.LP
1.6.10
\fICall Diversion (Call Forwarding) services\fR
.sp 1P
.RT
.sp 1P
.LP
1.6.10.1
\fICall Forwarding Busy\fR
.sp 9p
.RT
.PP
If user B is not NDUB, Call Waiting will take place. If user B is NDUB,
CFB will take place. Therefore these services are mutually exclusive and
there is no interaction.
.RT
.sp 1P
.LP
1.6.10.2
\fICall Forwarding No Reply\fR
.sp 9p
.RT
.PP
If subscriber B has Call Forwarding No Reply (CFNR) activated,
then a waiting call shall still be offered as described in this definition.
If no answer is received to this call within the duration of the CFNR timer,
then the CFNR service is invoked and the call is forwarded as per that
service
definition.
.RT
.sp 1P
.LP
1.6.10.3
\fICall Forwarding Unconditional\fR
.sp 9p
.RT
.PP
If subscriber B has activated Call Forwarding Unconditional, then the execution
of that forwarding condition takes precedence over Call Waiting.\fR Call
Forwarding Unconditional can be activated while a call is waiting without
changing the state of the waiting call.
.RT
.sp 1P
.LP
1.6.11
\fILine Hunting\fR
.sp 9p
.RT
.PP
The Call Waiting service should not be provided to a line in a hunt group.
.RT
.sp 1P
.LP
1.6.12
\fIThree\(hyParty Service\fR
.sp 9p
.RT
.PP
A user at B who is involved in a Three\(hyParty Service operation
(with minimal Three\(hyParty Service or active in a three\(hyway conversation)
may
receive an indication of a waiting call. The procedures and restrictions for
handling the waiting call are defined in the Three\(hyParty Service
description.
.RT
.sp 1P
.LP
1.6.13
\fIUser\(hyto\(hyUser Signalling\fR
.sp 9p
.RT
.PP
User\(hyto\(hyuser information (UUI) (service 1) included in the call
set\(hyup message will be delivered to subscriber B with the Call Waiting
indication.
.PP
UUI (service 2) sent from the calling user to the called user
during the alerting phase is allowed to be sent when a point\(hyto\(hypoint
configuration exists at the called side.
.PP
If the called user subscribes to User\(hyto\(hyUser Signalling, he may
include UUI (service 1) in a rejection of a waiting call when a point\(hyto\(hypoint
configuration exists at the called side.
.PP
There is no interaction with user\(hyto\(hyuser service 3.
.RT
.sp 1P
.LP
1.6.14
\fIMultiple Subscriber Number\fR
.sp 9p
.RT
.PP
No impact, i.e. neither supplementary service affects the
operation of the other supplementary service.
.RT
.sp 1P
.LP
1.6.15
\fICall Hold\fR
.sp 9p
.RT
.PP
When an ISDN user receives a call waiting indication the ISDN user may
use the Call Hold service to hold his active call and answer the waiting
call. Use of the hold service does not place a call into a waiting state.
.RT
.sp 1P
.LP
1.6.16
\fIAdvice of Charge\fR
.sp 9p
.RT
.PP
No impact, i.e. neither supplementary service affects the
operation of the other supplementary service.
.RT
.sp 2P
.LP
1.7
\fIDynamic description\fR
.sp 1P
.RT
.PP
The dynamic description of this service is given in
Figure\ 1/I.253.
.bp
.RT
.LP
.rs
.sp 47P
.ad r
\fBFigure 1/I.253 (feuillet 1 sur 5), (N), p.\fR
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.LP
.rs
.sp 47P
.ad r
\fBFigure 1/I.253 (feuillet 2 sur 5), (N), p. 2\fR
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.LP
.rs
.sp 47P
.ad r
\fBFigure 1/I.253 (feuillet 3 sur 5), (N), p. 3\fR
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.LP
.rs
.sp 47P
.ad r
\fBFigure 1/I.253 (feuillet 4 sur 5), (N), p. 4\fR
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.LP
.rs
.sp 38P
.ad r
\fBFigure 1/I.253 (feuillet 5 sur 5), (N), p. 5\fR
.sp 1P
.RT
.ad b
.RT
.sp 2P
.LP
\fB2\fR I.253.2\ \(em
\fBCall Hold\fR
.sp 1P
.RT
.sp 1P
.LP
2.1
\fIDefinition\fR
.sp 9p
.RT
.PP
The Call Hold service allows a user to interrupt communications on an existing
callB/Fconnection (Note 1) and then subsequently, if desired,
re\(hyestablish communications. A B\(hychannel (Note 2) may or may not
be reserved
after the communication is interrupted to allow the origination or possible
termination of other calls. Reservation must be provided by the service
provider as a user option. The Call Hold service includes the
Retrieve
operation
which re\(hyestablishes communication on a B\(hychannel between the
served user and the held party.
.PP
\fINote 1\fR \ \(em\ The applicability of the hold service to a \*Qcall\*U
versus a \*Qconnection\*U requires further study.
.PP
\fINote 2\fR \ \(em\ The applicability of this service definition to other
access resources (e.g.\ H\(hychannels, logical channels) for other services
requires further study.
.bp
.RT
.sp 2P
.LP
2.2
\fIDescription\fR
.sp 1P
.RT
.sp 1P
.LP
2.2.1
\fIGeneral description\fR
.sp 9p
.RT
.PP
When the Call Hold service is invoked, communication on a B\(hychannel
is interrupted and the B\(hychannel is released from use by the existing
call. If reservation is subscribed to, and depending on subscription parameters,
a
B\(hychannel is reserved for use by:
.RT
.LP
\(em
the given terminal used to invoke the Call Hold service;
.LP
\(em
a subscription time user\(hydefined set of terminals;
.LP
\(em
a user, defined by a directory number (Note);
.LP
\(em
a subscription time user\(hydefined set of directory numbers
(Note), or;
.LP
\(em
a user, identified by a Personal Identification Number
(Note).
.PP
\fINote\fR \ \(em\ Methods to define implementation are for further
study.
.PP
When a user (as identified by a terminal, others for further study)
places a call on hold and reservation applies, a B\(hychannel should always be
available on that user's interface so that the user may retrieve that call
from hold, or set up, retrieve or connect to another call. One B\(hychannel
should be kept available for the user as long as the user:
.RT
.LP
i)
has one or more calls on hold with
reservation
and
.LP
ii)
is not currently connected to any other
call.
.PP
Hence, the network should not reserve more than one B\(hychannel
for a user, regardless of how a user is defined (as identified by a terminal,
others for further study).
.PP
When the served user wishes to re\(hyestablish communications, the
Retrieve operation is requested. The success of the Retrieve operation
depends on whether a B\(hychannel was reserved and whether a B\(hychannel
is currently
available to the served user.
.RT
.sp 1P
.LP
2.2.2
\fISpecific terminology\fR
.sp 9p
.RT
.PP
None identified.
.RT
.sp 1P
.LP
2.2.3
\fIQualifications on the applicability to telecommunication\fR
\fIservices\fR
.sp 9p
.RT
.PP
This supplementary service is considered meaningful when applied to the
Telephony teleservice and the speech and 3.1\ kHz audio bearer services.
Furthermore, it may also be meaningful when applied to other services.
.RT
.sp 2P
.LP
2.3
\fIProcedures\fR
.sp 1P
.RT
.sp 1P
.LP
2.3.1
\fIProvisionB/Fwithdrawal\fR
.sp 9p
.RT
.PP
The type of reservation is specified at subscription time.
.RT
.sp 2P
.LP
2.3.2
\fINormal procedures\fR
.sp 1P
.RT
.sp 1P
.LP
2.3.2.1
\fIActivationB/FdeactivationB/Fregistration\fR
.sp 9p
.RT
.PP
None identified.
.RT
.sp 2P
.LP
2.3.2.2
\fIInvocation and operation\fR
.sp 1P
.RT
.sp 1P
.LP
2.3.2.2.1
\fIHold request\fR
.sp 9p
.RT
.PP
The served user indicates to the service provider that the
communication on the interface is to be interrupted. A call may be placed on
hold:
.RT
.LP
\(em
on the calling user's interface, by the calling user at any
time after completion of dialling;
.LP
\(em
on the called user's interface, by the called user at any
time after the call has been answered and before call
clearing has begun.
.PP
The communication on the interface is then interrupted. The
service provider acknowledges this action, and the associated channel is
made available for other uses, depending on the reservation option. As
an option, the network may send a notification to the held party indicating
that the call has been placed on hold.
.bp
.PP
If held call(s) are cleared for any reason, the service provider will continue
to reserve a channel for the specified user(s)/terminal(s) until there
are no more held calls with reservation associated with the specified
user(s)/terminal(s). If at any time a call is in the held state, either
party may clear the call.
.RT
.sp 1P
.LP
2.3.2.2.2
\fIRetrieve request\fR
.sp 9p
.RT
.PP
When the user who invoked the Call Hold service indicates that
the call is to be retrieved, the service provider will re\(hyestablish
communications, provided that a B\(hychannel is available, and acknowledge to
the served user and optionally to the held party that the call is now
active.
.PP
The user may optionally indicate a
B\(hychannel selection
parameter
in the Retrieve request. The parameter may
indicate:
.RT
.LP
1)
any channel is acceptable;
.LP
2)
specified channel is preferred; or
.LP
3)
specified channel is required exclusively.
.PP
If the service provider can satisfy the request, the call will be returned
to the active phase; if it cannot, the request will be rejected with the
appropriate cause returned to the user.
.sp 1P
.LP
2.3.2.2.3
\fIReservation processing\fR
.sp 9p
.RT
.PP
The following conditions concerning reservations against a channel apply:
.RT
.LP
1)
when the call is retrieved, any reservation against a
channel associated with that call should be cleared, regardless
of which channel is used to retrieve the call;
.LP
2)
when a call is cleared, any reservation against a
channel associated with the call should be cleared;
.LP
3)
when all reservations are cleared, all channels become
available for use by either the network or the user.
.LP
4)
When any reservation is outstanding for a given user
[as identified by a terminal, a set of terminals, a DN (directory number),
a set of DNs or a PIN (personal identification number)] and that
user is not using a channel for an active call, then the network must
consider a channel as \*Unot free\*U for that user for subsequent
incoming calls.
.LP
If all channels are \*Qnot free\*U (busy or reserved) and
a user has also subscribed to the Call Waiting service, the network would
be able to offer an incoming call with an indication that \*Qno interface
information channels are available\*U. The served user may accept that
incoming call using a reserved channel.
.sp 2P
.LP
2.3.3
\fIExceptional procedures\fR
.sp 1P
.RT
.sp 1P
.LP
2.3.3.1
\fIActivationB/FdeactivationB/Fregistration\fR
.sp 9p
.RT
.PP
None identified.
.RT
.sp 2P
.LP
2.3.3.2
\fIInvocation and operation\fR
.sp 1P
.RT
.sp 1P
.LP
2.3.3.2.1
\fIHold request\fR
.sp 9p
.RT
.PP
If the user tries to hold a call while not subscribed to the
service or if, for some other reason, the service provider cannot hold the
call, an indication will be provided to the user with the reason of
failure.
.RT
.sp 1P
.LP
2.3.3.2.2
\fIRetrieve request\fR
.sp 9p
.RT
.PP
If the service provider cannot retrieve a previously held call,
the user will be informed of the reason for failure. (For example, there may
not be any channel available, or the call may be in the process of being
cleared.)
.RT
.sp 1P
.LP
2.3.4
\fIAlternative procedures\fR
.sp 9p
.RT
.PP
None identified.
.RT
.sp 2P
.LP
2.4
\fINetwork capabilities for charging\fR
.sp 1P
.RT
.PP
This Recommendation does not cover charging principles. Future
Recommendations in the D\(hySeries are expected to contain that information.
.PP
It shall be possible to charge the subscriber accurately for the
service.
.bp
.RT
.sp 2P
.LP
2.5
\fIInterworking requirements\fR
.sp 1P
.RT
.PP
The operation of this feature is not affected by the nature
(i.e.\ ISDN or non\(hyISDN) of the far end of the connection.
.RT
.sp 2P
.LP
2.6
\fIInteractions with other supplementary services\fR
.sp 1P
.RT
.sp 1P
.LP
2.6.1
\fICall Waiting\fR
.sp 9p
.RT
.PP
A user may use the hold feature to hold an active call and answer an incoming
call that is being given call waiting treatment.
.RT
.sp 1P
.LP
2.6.2
\fICall Transfer\fR
.sp 9p
.RT
.PP
A served user may indicate to a service provider that a held call is to
be transferred to another party. The transfer indication must explicitly
identify the held call. A successful transfer will clear the held call
from the served user's point of view. For more information, see the explicit
call
transfer procedure in the Call Transfer service description.
.PP
Any parties on hold to a party being transferred will continue to
be on hold to that party after the transfer operation. For example, if
party\ B, currently active or on hold to party\ A, is transferred to another
party\ C by served user\ A, then the parties held by parties\ B and\ C
before the transfer will continue to be held by those parties after the
transfer.
.PP
The hold process is symmetric, i.e. both parties may place each other on
hold. It is possible, therefore, for two parties that have subscribed to
the Call Hold and Call Transfer services, to each place their active call
on hold and to simultaneously transfer the other party. That is, if parties\
A and\ B
have an active connection, party A may place the call on hold and transfer
party\ B to another party\ C while at the same time party\ B puts his call to
party\ A on hold and transfers party\ A to another party\ D.
.RT
.sp 1P
.LP
2.6.3
\fIConnected Line Identification Presentation\fR
.sp 9p
.RT
.PP
No impact, i.e. neither supplementary service affects the operation of
the other supplementary service.
.RT
.sp 1P
.LP
2.6.4
\fIConnected Line Identification Restriction\fR
.sp 9p
.RT
.PP
No impact, i.e. neither supplementary service affects the operation of
the other supplementary service.
.RT
.sp 1P
.LP
2.6.5
\fICalling Line Identification Presentation\fR
.sp 9p
.RT
.PP
No impact, i.e. neither supplementary service affects the operation of
the other supplementary service.
.RT
.sp 1P
.LP
2.6.6.
\fICalling Line Identification Restriction\fR
.sp 9p
.RT
.PP
No impact, i.e. neither supplementary service affects the
operation of the other supplementary service.
.RT
.sp 1P
.LP
2.6.7
\fIClosed User Group\fR
.sp 9p
.RT
.PP
No impact, i.e. neither supplementary service affects the
operation of the other supplementary service.
.RT
.sp 1P
.LP
2.6.8
\fIConference Calling\fR
.sp 9p
.RT
.PP
Any party involved in an active conference (i.e. the conference
controller or a conferee) may place the conference call on hold and later
retrieve the connection to the conference. Any party placing the conference
on hold may retrieve any other party it had previously placed on hold.
See also
the Conference Calling service description Recommendation\ I.254,
\(sc\ 1.6.15.
.bp
.RT
.sp 1P
.LP
2.6.9
\fIDirect Dialling\(hyIn\fR
.sp 9p
.RT
.PP
No impact, i.e. neither supplementary service affects the
operation of the other supplementary service.
.RT
.sp 2P
.LP
2.6.10
\fICall Diversion (i.e. Call Forwarding) services\fR
.sp 1P
.RT
.sp 1P
.LP
2.6.10.1
\fICall Forwarding Busy\fR
.sp 9p
.RT
.PP
No impact, i.e. neither supplementary service affects the operation of
the other supplementary service.
.RT
.sp 1P
.LP
2.6.10.2
\fICall Forwarding No Reply\fR
.sp 9p
.RT
.PP
No impact, i.e. neither supplementary service affects the operation of
the other supplementary service.
.RT
.sp 1P
.LP
2.6.10.3
\fICall Forwarding Unconditional\fR
.sp 9p
.RT
.PP
No impact, i.e. neither supplementary service affects the operation of
the other supplementary service.
.RT
.sp 1P
.LP
2.6.11
\fILine Hunting\fR
.sp 9p
.RT
.PP
No impact, i.e. neither supplementary service affects the operation of
the other supplementary service.
.RT
.sp 1P
.LP
2.6.12
\fIThree\(hyParty Service\fR
.sp 9p
.RT
.PP
Refer to Recommendation\ I.254, \(sc\ 2.6.15, interaction with Call
Hold.
.RT
.sp 1P
.LP
2.6.13
\fIUser\(hyto\(hyUser Signalling\fR
.sp 9p
.RT
.PP
Any party that has placed one or more calls on hold may continue to exchange
(send or receive) user\(hyto\(hyuser information (UUI) (service 3) messages
with the party(s) on hold as well as to exchange UUI
(service\ 3) messages
with
an active call party. A held party that is disconnecting may receive or send
UUI (service\ 1) messages during the clearing phase of the call.
.RT
.sp 1P
.LP
2.6.14
\fIMultiple Subscriber Number\fR
.sp 9p
.RT
.PP
No impact, i.e. neither supplementary service affects the operation of
the other supplementary service.
.RT
.sp 1P
.LP
2.6.15
\fICall Hold\fR
.sp 9p
.RT
.PP
Assume that parties A and B have both subscribed to the Call Hold service.
The Hold service is unidirectional and therefore, the following is
possible:
.RT
.LP
1)
only party A has party B on hold;
.LP
2)
only party B has party A on hold;
.LP
3)
each party has the other party on hold.
.sp 1P
.LP
2.6.16
\fIAdvice of Charge\fR
.sp 9p
.RT
.PP
No impact, i.e. neither supplementary service affects the operation of
the other supplementary service.
.RT
.sp 2P
.LP
2.7
\fIDynamic description\fR
.sp 1P
.RT
.PP
The dynamic description of this service is given in
Figure\ 2/I.253.
.RT
.sp 2P
.LP
\fB3\fR I.253.3\ \(em
\fBCompletion of Calls to Busy Subscribers\fR
.sp 1P
.RT
.PP
This service, already identified, needs to be further studied; its description
is not yet included.
.bp
.RT
.LP
.rs
.sp 47P
.ad r
\fBFigure 2/I.253 (feuillet 1 sur 2), (N), p.\fR
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.LP
.rs
.sp 47P
.ad r
\fBFigure 2/I.253 (feuillet 2 sur 2), (N), p.\fR
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.sp 2P
.LP
\fBRecommendation\ I.254\fR
.RT
.sp 2P
.sp 1P
.ce 1000
\fBMULTIPARTY\ SUPPLEMENTARY\ SERVICES\fR
.EF '% Fascicle\ III.7\ \(em\ Rec.\ I.254''
.OF '''Fascicle\ III.7\ \(em\ Rec.\ I.254 %'
.ce 0
.sp 1P
.ce 1000
\fI(Melbourne, 1988)\fR
.sp 9p
.RT
.ce 0
.sp 1P
.PP
The purpose of this Recommendation is to provide the stage 1 description
of the method defined in Recommendation\ I.130 using the means given in
Recommendation\ I.210.
.sp 1P
.RT
.PP
Supplementary services are described by a prose definition and
description (step\ 1.1) and by a dynamic description (step\ 1.3). The application
of the attribute technique (step\ 1.2), as defined in Recommendation I.140,
for supplementary services is for further study.
.PP
This Recommendation describes the following Multiparty Supplementary Services:
.RT
.LP
I.254.1
Conference Calling (CONF)
.LP
I.254.2
Three\(hyParty Service (3PTY)
.sp 2P
.LP
\fB1\fR I.254.1\ \(em
\fBConference Calling Service Description\fR
.sp 1P
.RT
.sp 1P
.LP
1.1
\fIDefinition\fR
.sp 9p
.RT
.PP
Conference Calling is an ISDN supplementary service which allows a user
to communicate simultaneously with multiple parties, which may also
communicate among themselves. This description deals primarily with the
establishment and manipulation of the connections used to form a conference
call and is therefore expected to be applicable to many types of conference
calls (e.g.\ voice, data, video, multi\(hymedia). Although provision is
made for
specifying the conference type, it is recognized that the control of
conferencing functions (especially for those other than speech) is beyond
the scope of this Recommendation.
.PP
This Recommendation describes the operation of the \*QAdd\(hyon\*U Conference
Calling service only. Other forms of Conference Calling (e.g.\ \*QMeet\(hyme\*U)
are
not described.
.RT
.sp 2P
.LP
1.2
\fIDescription\fR
.sp 1P
.RT
.sp 1P
.LP
1.2.1
\fIGeneral description\fR
.sp 9p
.RT
.PP
When Conference Calling is invoked, conference resources (e.g.\ a
\*Ubridge\*U) are allocated to the served user, and any calls indicated by the
service request are added to the conference. Once a conference is active,
parties may be added, dropped, isolated (i.e.\ prevented from communicating
with the conference), reattached, or split (i.e.\ removed from the conference
but
remain connected to the conference controller). The controller can place his
connection to the conference on hold, retrieve the conference, end the
conference, or disconnect himself from the conference.
.RT
.sp 2P
.LP
1.2.2
\fISpecific terminology\fR
.sp 1P
.RT
.sp 1P
.LP
1.2.2.1
\fIServed user, conference controller, conferees, parties\fR
.sp 9p
.RT
.PP
During the invocation phase, the service is under the control of
the \*Q
served user
\*U, i.e.\ the one for whom the service was subscribed or, in those cases
where subscription is not required, the one who invokes the
service. Once the conference is in the active state, the service is under
the control of the \*Q
conference controller
\*U who, in most cases, is
the served user but could be a party other than the served user if transfer
of control has occurred (an anticipated future extension to this service).
Any
party other than the conference controller is called a \*Q
conferee
\*U.
All participants in the conference call are considered
\*Qparties\*U.
.RT
.sp 1P
.LP
1.2.2.2
\fICall ID, Party ID, Connection ID\fR
.sp 9p
.RT
.PP
Call ID:\ the served user's (controller's) reference
to a call of which he is a party.
Examples:
.RT
.LP
1)
the conference call itself,
.LP
2)
a call which is to be added to the conference,
.LP
3)
a call which is formed by splitting a party from the
conference.
.bp
.PP
Party ID:\ the served user's (or controller's) reference to a
particular party within the context of a call.
.PP
Connection ID:\ the served user's (or controller's) reference to a \fR
particular connection (to a particular party) within the context of a call.
.PP
Observe that multiple parties may be associated with a given call,
e.g.\ a conference call. Moreover, there can be multiple connections associated
with a single party, e.g. a simultaneous voice and video call.
.PP
\fINote\fR \ \(em\ This service description assumes that there exists only
one connection to a given party. Procedures to allow for multiple connection
(e.g.\ multi\(hymedia conference calls) to a given party are anticipated future
extensions.
.RT
.sp 1P
.LP
1.2.2.3
\fIConference states\fR
.sp 9p
.RT
.PP
Conference Idle
:\ the state prior to the reception of a
\*Qconference invocation request
\*U, or after a particular conference has ended.
.PP
Conference Active
:\ the state in which conference resources
have been allocated to the specified conference and at least one party has a
connection to the conference. That connection could be either active or held.
.PP
Conference Floating
:\ the state in which the conference is
active but without a controller. This state is possible when two or more
conferees exist on an active conference and the controller successfully
disconnects himself (see Figure\ 1/I.254, sheet\ 7).
.RT
.sp 1P
.LP
1.2.3
\fIQualification on the applicability to telecommunication services\fR
.sp 9p
.RT
.PP
This supplementary service is considered meaningful when
applied to the Telephony teleservice and the speech and 3.1\ kHz audio bearer
services. Furthermore, it may also be meaningful when applied to other
services.
.RT
.sp 2P
.LP
1.3
\fIProcedures\fR
.sp 1P
.RT
.sp 1P
.LP
1.3.1
\fIProvision/withdrawal\fR
.sp 9p
.RT
.PP
The Conference Calling supplementary service may be subscribed to by prior
arrangements with the service provider. The subscription parameters
include the maximum (and, if different, the default) number of conferees
allowed in a conference call.
.PP
\fINote\fR \ \(em\ The default will usually be three, but may be six (or some
other number).
.PP
If the served user has subscribed to more than one size conference
service and wishes to establish a conference of a size other than the default
size, the served user must request the properly\(hysized conference before
any
parties are added to the conference.
.PP
Withdrawal of the service is made by the service provider upon request
by the subscriber or for service provider reasons.
.RT
.sp 2P
.LP
1.3.2
\fINormal procedures\fR
.sp 1P
.RT
.sp 1P
.LP
1.3.2.1
\fIActivation/deactivation/registration\fR
.sp 9p
.RT
.PP
None identified.
.RT
.sp 2P
.LP
1.3.2.2
\fIInvocation and operation\fR
.sp 1P
.RT
.sp 1P
.LP
1.3.2.2.1
\fIBeginning the conference call\fR | (see Figure 1/I.254, Sheets 1 and 2)
.sp 9p
.RT
.PP
\fIInvocation parameters:\fR
.PP
The Conference Calling service must be invoked by the served user.
The invocation request must include the \*Qroot\*U Call ID, i.e.\ the Call
ID by
which the served user (or controller) will refer to the conference call
itself. This Call ID may be either a new Call ID or the Call ID of an existing
call
which is to be used to form the conference.
.bp
.PP
The invocation request may include the following additional
information:
.RT
.LP
\(em
Conference size
:\ the intended maximum number of
parties for the conference (if different from the
default).
.LP
\(em
Existing call/party information
(Call IDs/Party
IDs/disposition of related B\(hychannel connections):\ in order to initially
include one or more parties from an existing call in the conference, the
invocation request must include the Call\ ID, and optionally the Party\ ID and
information as to how the B\(hychannel associated with that call is to be
handled.
.LP
\(em
New party information
(called party address, other
\*Qset\(hyup\*U information):\ in order to initially include a party for
which there is no existing call, the invocation request must include the
desired party's
address, and optionally other information information contained in a normal
call request.
.LP
\fI\fR
.LP
\fINote\fR \ \(em\ Some information which is mandatory in a
normal call request (e.g. \*Qbearer capability\*U) can be inferred
(e.g.\ from the conference type) and and hence may not be
mandatory here.
.LP
\(em
Connection request
:\ either active or held.
This request defines the served user's initial connection to the
conference. Possible values follow:
.LP
Active state specified
:
.LP
i)
Specific B\(hychannel
:\ a specified
preferred/exclusive B\(hychannel shall be used to immediately establish
a connection to the conference.
.LP
ii)
Any available B\(hychannel may be used.
.LP
Held state specified
:
.LP
i)
Reserved B\(hychannel
:\ a B\(hychannel is to be
reserved for (later) connection to the conference.
.LP
ii)
No reserved B\(hychannel
:\ in this case no
B\(hychannel is allocated or reserved; the served user may have to free up a
B\(hychannel later when participation in the conference is desired.
.LP
\(em
Conference type
:\ in general,
the bearer capability compatibility check during context arbitration can be
used to infer the type of conference required. It is assumed to be \*Qspeech\*U.
Other conference types may require special bridging facilities and/or higher
layer control.
.LP
\(em
Conference bridge location
:\ it should be possible to request the conference bridge to be at a specified
location, e.g.\ close to
some grouping of conferees. Procedures for remote location of conference
bridge facilities are anticipated future extensions.
.sp 1P
.LP
\fIDefaults for invocation parameters\fR
.sp 9p
.RT
.PP
If any of the information described above is not included in the
invocation request, the following defaults will occur:
.RT
.LP
\(em
Conference size:\ the size defaults to the subscribed default conference
size specified at subscription time (if the served user specified a default
conference size at subscription time) or the subscribed maximum
conference size (if a default conference size was not specified), or the
default conference size specified by the service provider (if the served
user did not subscribe to the service).
.LP
\(em
Existing call/party information:
.LP
i)
Call IDs:\ if no Call ID other than the root Call ID is specified, no
existing calls will be initially included in the conference.
.LP
ii)
Party IDs:\ if not specified, each party (other than
the served user) of the indicated Call\ ID(s) will be initially included
in the conference.
.LP
iii)
Disposition of related B\(hychannel
connections:\ if disposition information is not included, the related
B\(hychannel connections will be deallocated, unless the service
provider chooses to use them for connection of the served user to the
conference call (e.g.\ in a multi\(hymedia conference).
.LP
\(em
New party information:
.LP
i)
Called party address: if not specified, no new parties will be initially
included in the conference.
.LP
ii)
Other \*Qset\(hyup\*U information: for further
study.
.bp
.LP
\(em
Connection request:\ if no connection information is included, it is
assumed that the served user wishes to be initially connected
to the conference in the active state and any available B\(hychannel
may be used.
.LP
i)
If the served user indicates that he wishes to be
connected to the conference in the active state but does
not indicate \*Qspecific B\(hychannel\*U or \*Qany available B\(hychannel\*U,
it is assumed that any available B\(hychannel may be used.
.LP
ii)
If the served user indicates that he wishes his
resulting connection to the conference to be in the held state, but
does not indicate \*Qreserved B\(hychannel\*U nor \*Qno reserved\*U, it
is assumed
that a B\(hychannel is to be reserved for (later) connection
to the conference.
.LP
\(em
Conference type:\ if not specified, the service provider
will attempt to derive the appropriate conference type from the bearer
capabilities of the call(s) involved. If no calls are known
by the service provider to be involved in the call, the default conference
type shall be \*Qspeech\*U.
.LP
\(em
Conference bridge location
:\ if not specified, the
service provider will attempt to place the
conference bridge
(s) in the most appropriate location, considering the call(s) known by
the service
provider to be involved at the time the request is made.
.sp 1P
.LP
\fIProcedures\fR
.sp 9p
.RT
.PP
When a conference request is made, a conference call is
set up.
.PP
When the service provider receives the request to allocate resources for
the conference call, it checks to see that the requested conference can
be established. This procedure is termed \*Q
context arbitration
\*U. Context
arbitration includes a bearer capability compatibility check, a supplementary
services compatibility check, a check to see that the state of each connection
to be added is acceptable, and a check for the availability of
conference/network resources. Upon successful completion of the context
arbitration, the resources needed are allocated.
.PP
If the conference request is successful, all existing appropriate
call(s) referenced in the conference request are added to the
conference.
.PP
\fINote\fR \ \(em\ Adding parties from an existing call may not be successful
in all cases due to remote bridging and rerouting limitations.
.PP
Upon successful joining of the specified parties to the conference,
any unused B\(hychannels are deallocated and any single party calls are
released.
.PP
The service provider checks the conference request for additional
information (optional parameters). For those optional parameters not included
in the conference request, the default values will be used. In addition,
if the connection request parameter is not included and no additional parties
are
indicated (i.e.\ m\ =\ 0, n\ =\ 0) the service provider will prompt the
served user for further actions.
.RT
.LP
1)
Prompting procedures detected:\ if the number of referenced existing
calls (other than the root Call\ ID) in the conference request is zero
and the controller connection request is not included, then the conference
is put on hold from the served user's point of view and the served user
is
prompted for further actions (i.e.\ the add\(hyparty procedure is automatically
started).
.LP
2)
No prompting procedures detected:\ if the number of
referenced existing calls (other than the root Call\ ID) in the conference
request is larger than zero, or if the controller connection request is
specified, the referenced calls are automatically connected to the conference,
which is now in an active state. The served user's connection to the conference
will also be active unless the controller has indicated that his connection
to the conference should be held.
.LP
The decision to put the conference on hold or not (from the served user's
point of view) is based on the information received in the
Conference request, independent of the number of referenced existing
calls.
.sp 1P
.LP
1.3.2.2.2
\fIManaging individual parties\fR | (see Figure 1/I.254,
Sheets 2 and 3)
.sp 9p
.RT
.PP
When managing a party, the controller needs to specify the pair
Call\ ID/Party\ ID. If no party(s) is specified, the service provider will
typically assume that the request applies to all parties associated with the
indicated Call\ ID. (Exception: if Party\ ID is not specified in the drop
party command, the last party added to conference is dropped.)
.bp
.PP
In the active state of the conference, the conference controller has the
following options for managing parties in association with a
conference:
.RT
.sp 1P
.LP
\fIAdd new party\fR
.sp 9p
.RT
.PP
The conference controller can request that a new party be added to an existing
conference call using procedures analogous to those used to start the conference
call.
.PP
Upon a request for the addition of a new party, the conference
controller automatically puts the conference on hold. The service provider
checks the Add Party request for additional information, i.e.\ whether or not
the conference controller is to keep the conference on hold after the addition
of a new party. If no information is received, the service provider will
use
the service default value.
.PP
When on hold, the conference controller can either indicate the
address of a new party or indicate a Call\ ID of an already existing call.
(See Figure\ 1/I.254, Sheet\ 2.)
.RT
.LP
a)
New call:\ the service provider will establish a connection with the
new party indicated by the address provided by
the controller. Upon call establishment, the controller
will be connected to this new active call. (If call establishment
fails or if the active call is disconnected, the
controller may or may not return to the active
conference based on the connection request parameter within
the Add Party request).
.LP
\fINote\fR \ \(em\ By establishing this connection
via the conference bridge, the service provider may avoid
problems associated with remote bridging and rerouting.
.LP
b)
Existing call:\ if a Call ID exists, the controller indicates a call
Call\ ID to be added directly to the conference. The
party (parties) on the indicated call are immediately
joined to the conference.
.LP
If a Party ID is given in conjunction with the Call ID,
then the specified party is split from the specified call and added to the
conference. If no Party\ ID is given then all parties on the specified
call are added to the conference.
.LP
\fINote\fR \ \(em\ Adding parties from an existing call may not be
successful in all cases due to remote bridging and rerouting
limitations.
.sp 1P
.LP
\fIDrop party\fR
.sp 9p
.RT
.PP
The conference controller can request that a specified party be
disconnected from the conference and the conference controller's association
with that party be eliminated completely. If no Party\ ID is specified, it is
assumed that the last party (if identifiable) added to the conference should
be dropped. After the party is dropped, if there are no other conferees
(a
conferee being a party \fIother\fR than the conference controller), then the
conference remains in the Conference Active state (with only the conference
controller attached). If, after the party is dropped, there is only one
other conferee, then the service provider could, at its option, form an
\*Qordinary\*U
two\(hyparty call and release the conference resources, or remain in the
Conference Active state (with only the conference controller and the one
conferee attached). (See Figure\ 1/I.254, Sheet\ 3.)
.RT
.sp 1P
.LP
\fISplit party\fR
.sp 9p
.RT
.PP
The conference controller can request that a specified party be
removed from the conference but remain connected to the conference controller.
Execution of this request requires that the network establish a new Call\
ID for the call between the conference controller and the specified party,
since that party is no longer associated with the conference call. Two
parameters must
appear in the Split Party request:
.RT
.LP
1)
Call ID (conference call), and
.LP
2)
Party ID (specified party).
.PP
The Split Party request will put the controller's connection to
the conference in the held state and the controller's connection to the
specified party in the active state (see Figure\ 1/I.254, Sheet\ 3).
.sp 1P
.LP
\fIIsolate party\fR
.sp 9p
.RT
.PP
The conference controller can request that a specified party be
prevented from communicating with the conference but not removed from it.
This does not affect the state (e.g.\ active or held) of the specified
party's access channels (e.g.\ B\(hychannels) which are nominally under
the control of the
specified party. (See Figure\ 1/I.254, Sheet\ 3.)
.bp
.RT
.sp 1P
.LP
\fIReattach party\fR
.sp 9p
.RT
.PP
The conference controller can request that the specified party be reattached
to the conference. Successful execution of this command permits a
previously isolated party to again converse with all other parties that are
connected to the conference. (See Figure\ 1/I.254, Sheet\ 3.)
.RT
.sp 1P
.LP
1.3.2.2.3
\fIManaging the conference\fR | (see Figure 1/I.251, Sheets 4
and 5)
.sp 9p
.RT
.PP
In addition to the foregoing, the conference controller can manage the
complete conference in any of the following ways:
.RT
.LP
\fIHold conference:\fR \ the conference controller can request that his
own connection to the conference be held, using procedures as
described in the Call Hold service. Successful execution of this command
retains the existing state of conferees in relation to the conference,
i.e.\ those who could communicate with each other can still do so and those
who were in an isolated state remain in that state. (See Figure\ 1/I.254,
Sheet\ 4.)
.LP
\fIRetrieve conference:\fR \ the conference controller can
request that a conference controller's connection to the conference be
retrieved (see hold conference description above). Successful execution
of this command retains the existing state of conferees, i.e.\ those who
could
communicate with each other can still do so between themselves as well
as the conference controller, and those who were in an isolated state remain
in that state. (See Figure\ 1/I.254, Sheet\ 4.)
.LP
\fIInterrogate:\fR \ it is an anticipated future extension that the conference
controller will be able to request the current status of the
conference call (i.e.\ number of parties, identification of parties,\ etc.)
from the service provider. Information content and procedures for the interrogate
request are, as yet, undefined. (See Figure\ 1/I.254, Sheet\ 4.)
.LP
\fIDisconnect:\fR \ a Disconnect request from the controller
will disconnect the controller from the conference, and may, in some cases,
result in ending the conference. From the controller's perspective, this
disconnect procedure is identical to that outlined in the Basic Call service
description.
.LP
If:
.LP
a)
the number of conferees is greater than or equal to 2; and
.LP
b)
the Conference Floating option is subscribed to; and
.LP
c)
Floating conditions (e.g. charging) are satisfied;
.LP
then the conference goes to the Floating state. Otherwise the
conference ends (see End conference). This procedure differs from the
disconnect controller procedure in that the normal disconnect procedure can
result in either the Conference Active or Conference Idle state. When
Conference Floating cannot be performed, instead of notifying the controller,
disconnect processing continues with the release of conference resources.
(See Figure\ 1/I.254, Sheet\ 5.)
.LP
\fIDisconnect controller:\fR \ the controller can request that he be
disconnected from the conference. If the number of parties is greater
than or equal to 3 and if the controller has subscribed to the Conference
Floating option, and provided charging or other restrictions are not violated,
the connection of the controller will be cleared and the conference will
proceed to the Floating state (i.e.\ the remaining conferees may continue to
communicate). Otherwise, the controller will be notified that the Disconnect
Controller request is denied and the conference will remain active with the
controller still connected.
.LP
The remaining parties will stay on the conference without a
controller until less than two conferees exist on the conference. In a
conference without a controller, conferees can only hold, retrieve or drop
their own connections.
.LP
If one or two parties (including the controller)
exist on the conference at the time disconnect is requested,
the controller will be notified that the Disconnect
request is denied and the conference will remain active with
the controller still connected. (See Figure\ 1/I.254, Sheet\ 5.)
.LP
End conference:\ the conference controller can request that the
conference be terminated, i.e.
.LP
1)
that every party associated with a particular conference be disconnected,
.LP
2)
that all conference resources be de\(hyallocated, and
.LP
3)
that all knowledge of the conference call, including the
Call\ ID, be removed. (See Figure\ 1/I.254, Sheet\ 5.)
.PP
\fINote\fR \ \(em\ While Disconnect Controller and End Conference
provide useful unambiguous functions, it is recommended that all terminals
include the Disconnect function, and that this be the request that is sent
in response to the normal user action (e.g.\ hanging up the telephone).
This will avoid the problem which arises if the controller \*Qhangs up\*U
and leaves the
terminal before receiving notification that a Disconnect Controller request
cannot be accomplished. The Disconnect request would allow processing to
continue at this point and the conference would be ended.
.bp
.sp 1P
.LP
1.3.2.2.4
\fIPossible actions by conferees\fR | (See Figure 1/I.254,
Sheet 6)
.sp 9p
.RT
.PP
In the active state of the conference, the conference
can:
.RT
.LP
Hold/retrieve:\ put his connection to the conference on hold and
later retrieve it. (See Figure\ 1/I.254, Sheet\ 6.)
.LP
Disconnect from the conference:\ the procedures here are nominally the
same as those that occur after a conferee has been dropped from a
conference by the conference controller. (See Figure\ 1/I.254,
Sheet\ 6).
.PP
Indication of the above actions by any conferee should be provided to the
conference controller. Whether conferees also receive indications as to
the actions of other conferees is for further study.
.sp 2P
.LP
1.3.3
\fIExceptional procedures\fR
.sp 1P
.RT
.sp 1P
.LP
1.3.3.1
\fIActivation/deactivation/registration\fR
.sp 9p
.RT
.PP
None identified.
.RT
.sp 2P
.LP
1.3.3.2
\fIInvocation and operation\fR
.sp 1P
.RT
.sp 1P
.LP
1.3.3.2.1
\fIBeginning the conference call\fR
.sp 9p
.RT
.PP
If a user tries to invoke Conference Calling and the service
provider cannot comply with that request, the service provider will deny the
request and explain the reason for denial. Possible reasons for non\(hycompliance
are:
.RT
.LP
\(em
service not subscribed;
.LP
\(em
resources cannot be allocated;
.LP
\(em
served user (or intended conferee) restrictions not met;
.LP
\(em
context arbitration check failed;
.LP
\(em
more than one party in an alerting state.
.PP
If multiple conferees are specified in the conference request and if the
context arbitration failed for only a subset of the intended conferees,
the service provider has the option of permitting the subset of conferees
which passed the context arbitration to form the initial conference call.
If this is not permitted, the failure of any of the requested parties to
pass the context arbitration check causes the conference request to be
denied.
.sp 2P
.LP
1.3.3.2.2
\fIManaging individual parties\fR
.sp 1P
.RT
.sp 1P
.LP
\fIAdd new party:\fR | if the service provider cannot satisfy an
Add New Party request (e.g.\ if the conference call has been cleared or
if the maximum number of conferees allowed has already been reached) the
conference
controller will receive indication that the request is denied, with the
reason for failure.
.sp 9p
.RT
.LP
\fINote\fR \ \(em\ It is an anticipated future extension to allow for
conference re\(hysizing when there is an attempt to exceed the maximum
conference size allowed.
.LP
Failure to pass any of the checks associated with the context
arbitration results in the return of a failure message to the conference
controller with appropriate cause(s).
.LP
\fISplit isolate party:\fR \ if no Party ID is included in a
Split Party or Isolate Party request, notification of failure is returned to
the conference controller. If the controller sends an Isolate Party request
concerning a party which is already isolated, or a Re\(hyattach Party request
concerning a party which is already attached, the network will ignore the
request.
.sp 1P
.LP
1.3.3.2.3
\fIManaging the conference\fR
.sp 9p
.RT
.PP
No exceptional procedures identified.
.RT
.sp 1P
.LP
1.3.4
\fIAlternative procedures\fR
.sp 9p
.RT
.PP
None identified.
.bp
.RT
.LP
.rs
.sp 47P
.ad r
\fBFigure 1/I.254 (feuillet 1 sur 7), (N), p. 8\fR
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.LP
.rs
.sp 47P
.ad r
\fBFigure 1/I.254 (feuillet 2 sur 7), (N), p. 9\fR
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.LP
.rs
.sp 47P
.ad r
\fBFigure 1/I.254 (feuillet 3 sur 7), (N), p. 10\fR
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.LP
.rs
.sp 47P
.ad r
\fBFigure 1/I.254 (feuillet 4 sur 7), (N), p. 11\fR
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.LP
.rs
.sp 47P
.ad r
\fBFigure 1/I.254 (feuillet 5 sur 7), (N), p. 12\fR
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.LP
.rs
.sp 47P
.ad r
\fBFigure 1/I.254 (feuillet 6 sur 7), (N), p. 13\fR
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.LP
.rs
.sp 47P
.ad r
\fBFigure 1/I.254 (feuillet 7 sur 7), (N), p. 14\fR
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.sp 2P
.LP
1.4
\fINetwork capabilities for charging\fR
.sp 1P
.RT
.PP
This Recommendation does not cover charging principles. Future
Recommendations in the D\(hySeries are expected to contain that information.
.PP
It shall be possible to charge the subscriber accurately for the
service.
.RT
.sp 2P
.LP
1.5
\fIInterworking requirements\fR
.sp 1P
.RT
.PP
None identified.
.RT
.sp 2P
.LP
1.6
\fIInteractions with other supplementary services\fR
.sp 1P
.RT
.sp 1P
.LP
1.6.1
\fICall Waiting\fR
.sp 9p
.RT
.PP
Once a conference has been established of which the parties have
subscribed to the Call Waiting service:
.RT
.LP
i)
any party that has activated Call Waiting will be able to
receive an indication of an incoming call, and could place the conference on
hold to accept the waiting call;
.LP
ii)
the conference controller may, if desired, add the party
from the waiting call by answering the waiting call and using the \*Qadd party
from existing call\*U procedures.
.PP
\fINote\fR \ \(em\ If either the conference controller or a conferee has
accepted a waiting call and has subscribed to either (minimal) Three\(hyParty
service or Call Hold service, then this party could alternate between the
waiting call and the conference.
.sp 2P
.LP
1.6.2
\fICall Transfer\fR
.sp 1P
.RT
.sp 1P
.LP
\fIConference controller\fR
.sp 9p
.RT
.PP
A conference controller may transfer the conference to a party not in the
conference, but \*Qcontrol\*U cannot be transferred [Figure\ 2/I.254,
case\ a)]. The transfer of control of a conference to another party in the
conference is an anticipated future extension [Figure\ 2/I.254, case\ b)] not
yet included in this service description. A conference controller may
disconnect himself from the conference [Figure\ 2/I.254, case\ c)]
which may result in the conference entering a Floating state
(see \(sc\ 1.3.2.2.3).
.RT
.sp 1P
.LP
\fIConferee\fR
.sp 9p
.RT
.PP
A conferee should be able to transfer his connection to the
conference [Figure\ 2/I.254, case\ d)] to another party. Only the \*Qnormal\*U
and
\*Uexplicit\*U forms of transfer should be used, and the Complete Transfer
request should only be made after the call to the other party has reached
the active state. (This is to prevent call progress signals from disrupting
the
conference.) The identity of the new party, if available and unrestricted,
should be given to the conference controller.
.RT
.sp 1P
.LP
\fIAny party\fR
.sp 9p
.RT
.PP
Any party in a conference may transfer calls, or receive
transferred calls, that are independent from the conference. A conference
controller can add a call transferred to him using the \*Qadd party from
existing call\*U procedure [Figure\ 2/I.254, case\ e)] (see \(sc\ 1.3.2.2.2).
.PP
A conference controller can \*Qtransfer\*U a call to a conference
[Figure\ 2/I.254, case\ f)]. (This is functionally similar to the case
shown in Figure\ 2/I.254, case\ a).) A conferee may explicitly transfer
an incoming call that has reached the active state to a conference [Figure\
2/I.254, case\ f)],
but this results in the conferee being disconnected from the conference, as
shown in Figure\ 2/I.254, case\ d); it is not a form of \*Qadd party\*U.
.PP
Any party in a conference may place the conference on hold, and
explicity transfer another party that is being held. For example, user A is
active in a conference call and also has a party\ B on hold (B is thus not
part of the conference). User A may place the conference on hold and
\*Qexplicitly\*U transfer party B to another party.
.PP
Calls may be transferred to any party of a conference while that party
has the conference on hold. A conferee receiving a transferred call would
not be able to add the transferred party to the conference. A conference
controller receiving a transferred party would be able to use the \*Qadd
party from existing call\*U procedure to add this new party to the conference.
.bp
.RT
.LP
.rs
.sp 33P
.ad r
\fBFigure 2/I.254, (N), p.\fR
.sp 1P
.RT
.ad b
.RT
.sp 1P
.LP
1.6.3
\fIConnected Line Identification Presentation\fR
.sp 9p
.RT
.PP
A conference controller who has also subscribed to COLP should be presented
the connected party's number when the party is either part of the
initial activation of the conference or is added as a new conferee to an
existing conference. Conferees in an existing conference who have subscribed
to COLP will not receive a new party's number whenever a conference controller
adds a new party to the conference.
.RT
.sp 1P
.LP
1.6.4
\fIConnected Line Identification Restriction\fR
.sp 9p
.RT
.PP
No impact, i.e. neither supplementary service affects the operation of
the other supplementary service.
.RT
.sp 1P
.LP
1.6.5
\fICalling Line Identification Presentation\fR
.sp 9p
.RT
.PP
Any party that has subscribed to CLIP will receive the address of the conference
controller when:
.RT
.LP
\(em
the party is to be included as a \*Qnew party\*U during the
invocation of a conference call, or
.LP
\(em
the party is being added to an existing conference
call.
.bp
.sp 1P
.LP
1.6.6
\fICalling Line Identification Restriction\fR
.sp 9p
.RT
.PP
No impact, i.e. neither supplementary service affects the operation of
the other supplementary service.
.RT
.sp 1P
.LP
1.6.7
\fIClosed User Group\fR
.sp 9p
.RT
.PP
The conference controller and all conferees must belong to the same CUG.
When establishing the conference initially, or when adding a new conferee,
CUG restrictions must be checked and met for all parties on the conference
call before the (new) party is allowed to enter the conference.
.RT
.sp 1P
.LP
1.6.8
\fIConference Calling\fR
.sp 9p
.RT
.PP
A conferee may be connected to more than one conference if he has also
subscribed to the Hold service. The conferee could switch between the
conferences by placing one conference on hold and retrieving the other
conference. (See also \(sc\ 6.12 for the interaction with Three Party
Service).
.RT
.sp 1P
.LP
1.6.9
\fIDirect Dialling\(hyIn\fR
.sp 9p
.RT
.PP
No impact, i.e. neither supplementary service affects the operation of
the other supplementary service.
.RT
.sp 1P
.LP
1.6.10
\fICall Diversion (Call Forwarding) services\fR
.sp 9p
.RT
.PP
A call which has been diverted can be added to a conference by the conference
controller or be part of a new conference when initially invoked by the
served user.
.RT
.sp 1P
.LP
1.6.10.1
\fICall Forwarding Busy\fR
.sp 9p
.RT
.PP
See \(sc 1.6.10 above.
.RT
.sp 1P
.LP
1.6.10.2
\fICall Forwarding No Reply\fR
.sp 9p
.RT
.PP
See \(sc 1.6.10 above.
.RT
.sp 1P
.LP
1.6.10.3
\fICall Forwarding Unconditional\fR
.sp 9p
.RT
.PP
See \(sc 1.6.10 above.
.RT
.sp 1P
.LP
1.6.11
\fILine Hunting\fR
.sp 9p
.RT
.PP
No impact, i.e. neither supplementary service affects the operation of
the other supplementary service.
.RT
.sp 1P
.LP
1.6.12
\fIThree\(hyParty Service\fR (see Figure 3/I.254)
.sp 9p
.RT
.PP
It should be possible for a conference controller who has also
subscribed to (minimal) Three\(hyParty Service to participate in two conferences,
and alternate between them [Figure\ 3/I.254, case\ a)]. It should not be
possible to use (full) Three\(hyParty Service to join the two conferences
[Figure\ 3/I.254, case\ b)]. Procedures for joining conferences via normal
\*Qadd party\*U functions are described in the text.
.PP
It should be possible for a conferee who has also subscribed to
(minimal) Three\(hyParty Service to participate both in the conference and in
another call (which may or may not be a conference) and alternate between
them [Figure\ 3/I.254, case\ c)]. It is highly undesirable, and may, in
some
networks, be prohibited, for the conferee to use (full) Three\(hyParty
Service to bridge the conference and the other call [Figure\ 3/I.254, case\
d)]. This is
due to the reduced control the conference controller would have regarding
the party(ies) on the other call. Example: a conference controller request
to drop the conferee that invoked Three\(hyParty Service would drop the
conference
connection to all of the parties on that three\(hyway call [Figure\ 3/I.254,
case\ e)] but would not, in fact, disconnect any of them; they would remain
active with party\ C.
.bp
.RT
.LP
.rs
.sp 31P
.ad r
\fBFigure 3/I.254, (N), p.\fR
.sp 1P
.RT
.ad b
.RT
.sp 1P
.LP
1.6.13
\fIUser\(hyto\(hyUser Signalling\fR
.sp 9p
.RT
.PP
The conference controller will be able to send user\(hyto\(hyuser
information (UUI) (service\ 3) to any conferee on a conference call
individually, and in some networks optionally broadcast messages to all
conferees. (This assumes that each conferee can be uniquely identified.) UUI
can be received by the conference controller from any of the conferees.
While adding a new party to the conference, the conference controller can
send and
receive UUI (services\ 1, 2 and\ 3) from the new party until the new party is
added to the conference.
.PP
A conferee may send and receive UUI (service 3 and service 1 during
call clearing phase) from the conference controller. UUI cannot be sent
between the conferees in association with the conference call (although any
two parties, if subscribed, could send non\(hycall associated UUI to each
other.) A conferee's ability to send broadcast messages (under the control
of the
conference controller) to all parties, is for further study. A conferee may
send UUI (service\ 1) to the conference controller only during the call
clearing phase.
.RT
.sp 1P
.LP
1.6.14
\fIMultiple Subscriber Number\fR
.sp 9p
.RT
.PP
No impact, i.e. neither supplementary service affects the operation of
the other supplementary service.
.bp
.RT
.sp 1P
.LP
1.6.15
\fICall Hold\fR
.sp 9p
.RT
.PP
When establishing a conference, the served user may identify any
party(s) it has on hold to become a conferee(s) in the conference call being
established. Similarly, a conference controller may add any party he has on
hold to an active conference.
.PP
A party (A) in a conference may place the conference on hold and
retrieve some other party that party\ A has on hold. Party\ A may then
place this call on hold to retrieve the conference call.
.PP
Assuming subscription to both the Conference Calling and Call Hold
services, a party may:
.RT
.LP
i)
be a conference controller of two or more conferences. The conference
controller switches conferences by putting the active conference on hold
and then retrieving another conference;
.LP
ii)
be a conference controller of one conference and a
conferee of another conference(s). The party may switch between
conferences by putting the active conference on hold and then retrieving
another conference.
.sp 1P
.LP
1.6.16
\fIAdvice of Charge\fR
.sp 9p
.RT
.PP
No impact, i.e. neither supplementary service affects the operation of
the other supplementary service.
.RT
.sp 2P
.LP
1.7
\fIDynamic description\fR
.sp 1P
.RT
.PP
The dynamic description of this service is shown in
Figure\ 1/I.254, Sheets\ 1 to\ 7.
.RT
.sp 2P
.LP
\fB2\fR I.254.2\ \(em\
\fBThree Party Service\fR
.sp 1P
.RT
.sp 1P
.LP
2.1
\fIDefinition\fR
.sp 9p
.RT
.PP
The Three\(hyParty Service enables a user who is active on a call to hold
that call, make an additional call to a third party, switch from one call
to the other as required (privacy being provided between the two calls),
and/or release one call and return to the other. Optionally, the served
user could
subscribe to an ability to join the two calls together into a three\(hyway
conversation. (Relationships between this service and the Call Transfer
supplementary service are indicated throughout the text and
Figure\ 4/I.254).
.RT
.sp 2P
.LP
2.2
\fIDescription\fR
.sp 1P
.RT
.sp 1P
.LP
2.2.1
\fIGeneral description\fR
.sp 9p
.RT
.PP
Three\(hyParty Service provides a user with flexibility in handling up
to two (initially\(hy) independent calls. Different forms of the service
exist
which allow the user to control these calls. The various forms of Three\(hyParty
Service are given in Table\ 1/I.254.
.PP
In principle, all participants in a Three\(hyParty Service call should
be informed about the state of their calls whenever necessary.
.RT
.ce
\fBH.T. [T1.254]\fR
.ce
TABLE\ 1/X.254
.ps 9
.vs 11
.nr VS 11
.nr PS 9
.TS
center box;
cw(48p) | lw(96p) | cw(48p) .
Form of service {
\(em
Hold existing call
\(em
Make call to 3rd party
\(em
Alternate between parties
} {
Form common path between all three parties
}
_
.T&
lw(48p) | cw(96p) | cw(48p) .
Minimal service Yes No
_
.T&
lw(48p) | cw(96p) | cw(48p) .
Full three\(hyparty service Yes Yes
_
.TE
.nr PS 9
.RT
.ad r
\fBTable 1/I.254 [T1.254], p.\fR
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.sp 1P
.LP
2.2.2
\fISpecific terminology\fR
.sp 9p
.RT
.PP
Call ID:\ the served user's reference to a call of which he is a
party. Examples:
.RT
.LP
1)
the call to user B (or user C) prior to its being used to
form a three\(hyway conversation;
.LP
2)
the three\(hyway conversation, once it is formed.
.PP
Served user:\ during the invocation and active phases, the service is under
the control of the \*Qserved user\*U, i.e. the one for whom the service
was subscribed. This user is also referred to as \*Quser A\*U.
.PP
User B:\ The other party in the original call (A\(<-
\(raB).
.PP
User C:\ The \*Qthird party\*U \(em the other party in the second (e.g.
enquiry) call (A | (raC).
.PP
(For the original call, the served user may have been either the
calling or called party (i.e. it may have been either an incoming or outgoing
call)).
.RT
.sp 1P
.LP
2.2.3
\fIQualifications on the applicability to telecommunication\fR
\fIservices\fR
.sp 9p
.RT
.PP
This supplementary service is considered meaningful when applied to the
Telephony teleservice and the speech and 3.1\ kHz audio bearer services.
Furthermore, it may also be meaningful when applied to other
services.
.RT
.sp 2P
.LP
2.3
\fIProcedures\fR
.sp 1P
.RT
.sp 1P
.LP
2.3.1
\fIProvision/withdrawal\fR
.sp 9p
.RT
.PP
The Three\(hyParty supplementary service is subscribed to by prior
arrangements with the service provider. Subscription can be made for the
Minimal Service or the Full Three\(hyParty Service.
.PP
Withdrawal of the service is made by the service provider upon request
by the subscriber or for service provider reasons.
.RT
.sp 2P
.LP
2.3.2
\fINormal procedures\fR
.sp 1P
.RT
.sp 1P
.LP
2.3.2.1
\fIActivation/deactivation/registration\fR
.sp 9p
.RT
.PP
None identified.
.RT
.sp 2P
.LP
2.3.2.2
\fIInvocation and operation\fR
.sp 1P
.RT
.sp 1P
.LP
2.3.2.2.1
\fIBeginning Three\(hyParty Service\fR | (see Figure 4/I.254,
Sheet\ 1)
.sp 9p
.RT
.PP
The served user, user A, who has an existing active call with user B, asks
the service provider to begin the Three\(hyParty Service. The service
provider puts the existing call on hold. User\ A then proceeds to establish
the second call (to user\ C).
.PP
\fINote\fR \ \(em\ The same actions take place when the served user asks the
service provider to start the \*Qnormal\*U Call Transfer service (see Call
Transfer service description). Conceivably, a similar \*QHeld && Active\*U
service state
(see Figure\ 2/I.252) could be attained as a result of accepting an incoming
call in such a way that the service provider knew to associate that incoming
call with the existing call and, hence, put the existing call on hold (see
Call Waiting service description for one such possibility).
.RT
.sp 1P
.LP
2.3.2.2.2
\fIManaging two associated calls \(em one held one active\fR |
(see Figure\ 4/I.254, Sheets\ 1 and 2)
.sp 9p
.RT
.sp 1P
.LP
\fIServed user\fR :
.sp 9p
.RT
.PP
Once the call to the third party reaches the alerting state, the
served user can:
.RT
.LP
i)
alternate from one call to the other as required (possibly several times),
privacy being provided between the two calls;
.LP
\fINote\fR \ \(em\ The exact interactions between the served user and
the service provider depend somewhat on the information and control
capabilities available to the user from his terminal. Compare the two methods
of alternating between calls given in Figure\ 4/I.254 under \*QAlternate\*U
vs.
\*QReturn to B(C)\*U.
.bp
.LP
ii)
Disconnect the active party (e.g. user C), whereupon
the service provider would notify (see Note) the served user
that the other party (e.g.\ user\ B) is still held and wait
for one of the following events:
.LP
\(em
a request from the served user that the held
party be retrieved;
.LP
\(em
a request from held party to disconnect.
.LP
If neither event occurs within a brief time
interval, the service provider will disconnect the
held party.
.LP
\fINote\fR \ \(em\ This would be a \*Qhigh priority notify\*U,
i.e. one capable of gaining the served user's attention if he were
away from the terminal. Ringing is an example of this.
.LP
iii)
Disconnect the held party (e.g. user B)
.LP
\fINote\fR \ \(em\ Disconnecting a held party without
previously retrieving it is considered undesirable for a
\*Qhuman\(hyto\(hyhuman\*U call but may be
useful in other cases;
.LP
or, if subscribed for:
.LP
iv)
request the service provider to begin a three\(hyway
conversation (see managing an active three\(hyway
conversation below).
.LP
\fINote\fR \ \(em\ In some networks, the served user can
invoke this step only after the call to the third party
reaches the active state.
.sp 1P
.LP
\fIActive party\fR
.sp 9p
.RT
.PP
If the active party disconnects, the service provider would notify the
served user that the other party (e.g. user B) is still held and wait for
one of the following events:
.RT
.LP
\(em
a request from the served user that the held party be
retrieved;
.LP
\(em
a request from the held party to disconnect.
.PP
If neither event occurs within a brief time interval, the service provider
will disconnect the held party.
.sp 1P
.LP
\fIHeld party\fR
.sp 9p
.RT
.PP
If the held party disconnects, the service provider will clear that connection,
resulting in a simple active call between the served user and the currently\(hyactive
user.
.RT
.sp 1P
.LP
2.3.2.2.3
\fIManaging an active three\(hyway conversation\fR |
(See Figure 4/I.254, Sheet\ 3)
.sp 9p
.RT
.PP
\fINote\fR \ \(em\ The extent to which the service provider re\(hyuses the
existing resources (e.g.\ a bridge) to form the resulting, simple call is a
service provider option.
.RT
.sp 1P
.LP
\fIServed user\fR
.sp 9p
.RT
.PP
During an active three\(hyway conversation, the served user can
request that the service provider:
.RT
.LP
i)
end the three\(hyway conversation;
.LP
\fINote\fR \ \(em\ Signalling procedures for disconnecting a
multi\(hyconnection call are not yet defined.
.LP
ii)
disconnect himself from the three\(hyway conversation.
Since the served user is also the controller (and normally the
one that is charged for the call), this shall result in the entire
three\(hyway call being cleared.
.LP
\fINote\fR \ \(em\ An anticipated future extension to this
service and the Call Transfer service is the ability to negotiate
charging and control responsibilities, thus permitting the
call to continue after the served user has disconnected
(See Figure\ 4/I.254: call transfer from Active Three\(hyWay
Conversation state).
.LP
iii)
explicitly disconnect one of the other parties
which would result in a simple active call between the served
user and the remaining other party;
.LP
iv)
place his connection into the conversation on hold
(and, typically, later retrieve it).
.LP
\fINote\fR \ \(em\ While the served user is held, the other parties
(B and C) may continue to communicate.
.LP
v)
split off one of the parties in order to have a private
communication with that party. This results in that party
being split off from the conversation, the connection
between the served user and the other party on the three\(hyway
call being placed on hold, and the connection between the
served user and the designated party being
active.
.bp
.sp 1P
.LP
\fIOther party (B or C)\fR
.sp 9p
.RT
.PP
Either of the other parties (users B or C) can ask the service
provider to:
.RT
.LP
i)
release it from the three\(hyway conversation which results in
a simple active call between the served user and the
remaining party;
.LP
ii)
place its connection to the three\(hyway conversation
on hold (and, typically, later retrieve it);
.LP
\fINote\fR \ \(em\ While the served user is held, the other
parties (i.e. served user and remaining party) may continue
to communicate.
.sp 2P
.LP
2.3.3
\fIExceptional procedures\fR
.sp 1P
.RT
.sp 1P
.LP
2.3.3.1
\fIActivation/deactivation/registration\fR
.sp 9p
.RT
.PP
None identified.
.RT
.sp 1P
.LP
2.3.3.2
\fIInvocation and operation\fR
.sp 9p
.RT
.PP
None identified.
.RT
.sp 2P
.LP
2.3.4
\fIAlternative procedures\fR
.sp 1P
.RT
.sp 1P
.LP
2.3.4.1
\fIActivation/deactivation/registration\fR
.sp 9p
.RT
.PP
None identified.
.RT
.sp 1P
.LP
2.3.4.2
\fIInvocation and operation\fR
.sp 9p
.RT
.PP
None identified, except for the point made above regarding
variations due to different terminal capabilities.
.RT
.sp 2P
.LP
2.4
\fINetwork capabilities for charging\fR
.sp 1P
.RT
.PP
This Recommendation does not cover charging principles. Future
Recommendations in the D\(hySeries are expected to contain that information.
.PP
It shall be possible to charge the subscriber accurately
for the service.
.RT
.sp 2P
.LP
2.5
\fIInterworking Requirements\fR
.sp 1P
.RT
.PP
None identified.
.RT
.sp 2P
.LP
2.6
\fIInteraction with other supplementary services\fR
.sp 1P
.RT
.sp 1P
.LP
2.6.1
\fICall Waiting\fR
.sp 9p
.RT
.PP
Assume that users A, B and C have subscribed
to the Call Waiting service, then:
.RT
.LP
\(em
if a call waiting indication was presented to user A and/or
user\ B either before or during the Three\(hyparty\(hyService
invocation, then the call waiting indication would still be
present after the Three\(hyParty Service is active. While the
Three\(hyParty Service is active, the party with the waiting
call may put his active call on hold to accept the waiting
call;
.LP
\(em
a call waiting indication may be presented to any party
involved in a Three\(hyParty Service call, and that
party:
.LP
1)
may be active in a two\(hyparty call (A\(hyB or A\(hyC),
.LP
2)
may be on hold (B during A\(hyC, C during A\(hyB),
.LP
3)
may be active in a three\(hyway conversation, or
.LP
4)
may have his connection to the three\(hyway conversation
on hold;
.LP
\(em
it may be desirable to include a capability of accepting an
incoming call as part of Three\(hyParty Service. Currently a
user could alternate between the first call and the second
(waiting or answered) call by combining hold and retrieve
requests. A user could also join the second (waiting or
active) call to the first call by invoking a three\(hy (or more)
party conference call.
.bp
.sp 1P
.LP
2.6.2
\fICall Transfer\fR
.sp 9p
.RT
.PP
Call Transfer can be invoked in either the Held A\(<-
\(raB(C)
&& Active A | (raC(B) state (see Figure\ 2/I.252 for Call Transfer service)
or the Active Three\(hyWay Conversation state (see Figure\ 5/I.254, call
transfer from
Active Three\(hyWay Conversation state).
.RT
.sp 1P
.LP
2.6.3
\fIConnected Line Identification Presentation\fR
.sp 9p
.RT
.PP
No impact supplementary service affects the operation of
the other supplementary service.
.RT
.sp 1P
.LP
2.6.4
\fIConnected Line Identification Presentation\fR
.sp 9p
.RT
.PP
No impact, i.e. neither supplementary service affects the operation of
the other supplementary service.
.RT
.sp 1P
.LP
2.6.5
\fICalling Line Identification Presentation\fR
.sp 9p
.RT
.PP
No impact, i.e. neither supplementary service affects the operation of
the other supplementary service.
.RT
.sp 1P
.LP
2.6.6
\fICalling Line Identification Restriction\fR
.sp 9p
.RT
.PP
No impact, i.e. neither supplementary service affects the operation of
the other supplementary service.
.RT
.sp 1P
.LP
2.6.7
\fIClosed User Group\fR
.sp 9p
.RT
.PP
Assume that a user A, who has subscribed to the Three\(hyParty
Service, has an established call with user\ B and wishes to create a three\(hyparty
call by including a user\ C (either a minimum Three\(hyParty Service or
a three\(hyway conversation).
.PP
When user A invokes the Three\(hyParty Service and places a call to
user\ C, the service provider shall check that all CUG conditions are met
between users\ A and C but is \fInot\fR required to check CUG conditions
between
users\ B and C at this point since user\ A may wish to only have a minimal
Three\(hyParty Service call.
.PP
If any of the parties to be involved in the three\(hyparty call are also
a CUG member, then CUG conditions must be met by all of the parties before
a
three\(hyway conversation can be formed.
.RT
.sp 1P
.LP
2.6.8
\fIConference Calling\fR
.sp 9p
.RT
.PP
A served user who has invoked Three\(hyParty Service to create a
three\(hyway conversation may convert the three\(hyway conversation to
a conference call by invoking the Conference Calling Service and identifying
the Party\ IDs of the currently existing other two parties as part of the
conference
invocation. This requires that the served user of the Three\(hyParty Service
has also subscribed to the Conference Calling service. For other interactions,
see \(sc\ 1.6.12.
.RT
.sp 1P
.LP
2.6.9
\fIDirect Dialling\(hyIn\fR
.sp 9p
.RT
.PP
No impact, i.e. neither supplementary service affects the operation of
the other supplementary service.
.RT
.sp 1P
.LP
2.6.10
\fICall Diversion (Call Forwarding) services\fR
.sp 9p
.RT
.PP
If the served user attempts to establish the second call to a
user\ C who has Call Forwarding activated, and the appropriate forwarding
conditions are met, the forwarding\(hyto user will be alerted and treated
in all other respects as if the call had been placed to him.
.RT
.sp 1P
.LP
2.6.11
\fILine Hunting\fR
.sp 9p
.RT
.PP
No impact, i.e. neither supplementary service affects the operation of
the other supplementary service.
.bp
.RT
.sp 1P
.LP
2.6.12
\fIThree\(hyParty Service\fR
.sp 9p
.RT
.PP
The served user (A) may treat a Three\(hyParty Service call that has reached
the Three\(hyWay Conversation service state as an \*Qexisting call\*U upon
which the minimal Three\(hyParty Service may be invoked. That is, if the served
user\ A is in a three\(hyway conversation with parties\ B and\ C and invokes
(minimal) Three\(hyParty Service on it, the service provider will place
the served user's connection to the conversation on hold (with channel
reservation) and
allow the served user to establish a call to another party\ (D). Once the
call to user\ D reaches the alerting state, any of the procedures in \(sc\
2.3.2.2.2 may be used to manage the call to party\ D and the \*Qthree\(hyway
conversation\*U
call.
.RT
.sp 1P
.LP
2.6.13
\fIUser\(hyto\(hyUser Signalling\fR
.sp 9p
.RT
.PP
While adding the third party (user C) to the three\(hyparty service, the
served user (user\ A) can send and receive UUI (services\ 1, 2 and\ 3)
from the new party until the new party is added to a three\(hyway
conversation.
.PP
The served user will be able to send and receive UUI (service\ 3) to
both remote parties (users\ B and C) on a three\(hyway conversation individually
and in some networks optionally broadcast UUI (service\ 3) messages to both
parties (see Note). UUI (service\ 3) cannot be sent between remote parties
(users\ B and\ C) in association with the three\(hyway conversation.
.PP
\fINote\fR \ \(em\ This assumes that each party can be uniquely
identified.
.RT
.sp 1P
.LP
2.6.14
\fIMultiple Subscriber Number\fR
.sp 9p
.RT
.PP
No impact, i.e. neither supplementary service affects the operation of
the other supplementary service.
.RT
.sp 1P
.LP
2.6.15
\fICall Hold\fR
.sp 9p
.RT
.PP
A served user who has all of his parties on hold would not be
able to invoke the Three\(hyParty Service, since he is not active on any given
call.
.PP
A served user A engaged in an active call to a user\ B shall be able to
invoke the Three\(hyParty Service (if subscribed to) to a user\ C already
on hold to served user\ A. This will allow served user\ A to create a three\(hyway
conversation with user\ B and previously held user\ C.
.PP
Any party involved in a Three\(hyParty Service call (either minimum
service or a three\(hyway conversation) will be able to put the Three\(hyParty
Service call on hold. Once a party puts a Three\(hyParty Service call on hold,
that party may retrieve any other call it has previously held.
.PP
For any party involved in a three\(hyparty call which has also subscribed
to the hold service without channel reservation, that party may place the
Three\(hyParty Service on hold and
.RT
.LP
1)
initiate a new call;
.LP
2)
receive a call (e.g. to process a Call Waiting
request); or
.LP
3)
complete a call to a new free party that previously was
busy and for which the Completion of Calls to Busy
Subscribers (CCBS) had been invoked (see
Note).
.PP
\fINote\fR \ \(em\ The Completion of Calls to Busy Subscribers supplementary
service needs further study.
.PP
The Call Hold service allows a user to switch (by hold and retrieve) between
\*Uparties\*U where a party may be a single user, a three\(hyway conversation,
or a conference call. Thus, a party in a three\(hyway conversation may
switch
between the three\(hyway conversation and another \*Qparty\*U hold, the
\*Qparty\*U being a single user, another three\(hyparty call or a conference
call.
.RT
.sp 1P
.LP
2.6.16
\fIAdvice of Charge\fR
.sp 9p
.RT
.PP
No impact, i.e. neither supplementary service affects the operation of
the other supplementary services.
.RT
.sp 2P
.LP
2.7
\fIDynamic description\fR
.sp 1P
.RT
.PP
The dynamic description of this service is shown in
Figure 4/I.254.
.bp
.RT
.LP
.rs
.sp 47P
.ad r
\fBFigure 4/I.254 (feuillet 1 sur 3), (N), p. 18\fR
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.LP
.rs
.sp 47P
.ad r
\fBFigure 4/I.254 (feuillet 2 sur 3), (N), p. 19\fR
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.LP
.rs
.sp 47P
.ad r
\fBFigure 4/I.254 (feuillet 3 sur 3), (N), p. 20\fR
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.LP
.rs
.sp 47P
.ad r
\fBFigure 5/I.254, (N), p. 21\fR
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.LP
.rs
.sp 47P
.ad r
\fBFigure 6/I.254, (N), p. 22\fR
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.LP
.rs
.sp 47P
.ad r
\fBFigure 7/I.254, (N), p. 23\fR
.sp 1P
.RT
.ad b
.RT
.LP
.bp